MsDO Weekplan 12

The learning goals for Week 47 are:

Logging and Monitoring.

Literature:

• [Newman, 2015] Chapter 8
• [Nygard, 2017] p. 165--170
• [Bass et al., 2013] Monitorability (On BS)
• [Wiggins, 2017] Full article (Online)
• [Splunk (a), 2019] Full article (Online)
• [Splunk (b), 2019] Full article (Online)

Slides:

• W12-1 Monitoring (powerpoint) // (PDF)
• W12-2 Logging (powerpoint) // (PDF)
• W12-3 Docker Healthcheck (powerpoint) // (PDF)
• W12-4 Humio (powerpoint) // (PDF)

Notes for this weekplan:

Exercise 'healthcheck'

Goal: To play around with HEALTHCHECK in your docker file (or compose-file).

Dig out the old 'hello-spark' code (from Iteration 1's exercise 'docker-hello-spark') or pick your group's microservice (CaveService, PlayerService, MessageService) if you already have coded the REST service and created the Dockerfile.

Now, add a '/health' path to return a simple JSON object and status code 200 OK. Verify that it works, using 'curl' or 'httpie'.

Next, add a HEALTHCHECK entry in your Dockerfile, and use "docker ps" or "docker inspect --format='{{json .State.Health}}' (containername)" to follow the status of the container as it starts up.

Exercise 'humio-tutorial'

Register yourself for a 'Humio Community Edition' at www.humio.com / Cloud Login, and follow the built-in tutorial.

Exercise 'skycave-humio-logging'

Make your skycave daemon log its output to Humio. Start with the skycave daemon or your group's REST service. (Hints and hard-learned lessons in the W12-4 slides).

Cheatmode: Use the humio-parser as parser for the Henrik Bærbak logging format in default SkyCave.

Also the current daemon does not provide much interesting logging, so to enhance that, use these updated invokers:

1. CaveInvoker
2. PlayerInvoker

Exercise 'skycave-humio-dashboard'

Create a nice dashboard for Skycave monitoring, that Henrik can be use in the next MSDO course (amble acknowledgements will of course be given :).